Add tool for getting a single commit (includes stats, files)#216
Merged
Add tool for getting a single commit (includes stats, files)#216
Conversation
jshorty
requested review from
SamMorrowDrums,
juruen,
toby and
williammartin
as code owners
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new tool for retrieving detailed information about a single GitHub commit, including associated stats and file changes.
- Registers the new "get_commit" tool in the server configuration.
- Implements the tool in pkg/github/repositories.go with support for pagination.
- Adds corresponding tests in pkg/github/repositories_test.go and updates the README.
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| pkg/github/server.go | Added tool registration for get_commit |
| pkg/github/repositories_test.go | Added tests to verify proper behavior of the new get_commit tool |
| pkg/github/repositories.go | Implemented the get_commit tool with error handling and pagination |
| README.md | Updated documentation to include the new get_commit tool |
Comments suppressed due to low confidence (1)
pkg/github/repositories.go:18
- [nitpick] The translation key 'TOOL_GET_COMMITS_DESCRIPTION' uses the plural 'commits' while the tool is named 'get_commit'. Consider updating the key for consistency.
mcp.WithDescription(t("TOOL_GET_COMMITS_DESCRIPTION", "Get details for a commit from a GitHub repository")),
6122f7c to
334a981
Compare
nickytonline
pushed a commit
to nickytonline/github-mcp-http
that referenced
this pull request
Oct 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While we offer tools to list repo commits today, from an LLM perspective this relies heavily on the accuracy of the commit message to glean any meaning from it. A natural followup may be to dig deeper into a specific commit.
The existing "get commit" endpoint offered by our API allows for more detailed information, including the relative size of the change as well as the actual file changes.
Some similar data is available via
getPullRequestFilesbut this allows more granular/targeted querying.